Signed-off-by: Mike Turner <mike@provable.com>

Rename `kind` to `type` and `RecordMatcher` to `RecordFieldFilter`. Reframe
the permission model as additive: `programs` and `decryptPermission` are
preserved exactly, with `recordAccess` and `viewKeyExposure` as new opt-in
fields. Drop `anyProgram` level. Document backward-compatibility guarantees,
interaction rules, and validation failure modes.

Make readAddress optional with default true. Add an Address exposure
subsection covering all four address-leakage surfaces (connect return,
_publicKey getter, init handler, plaintext-bearing methods) and their
behavior under readAddress: false. Document the decryptPermission:
NoDecrypt-only constraint and the deliberate signMessage leak.

Adds the dapp-facing types and signature changes from
docs/adapter-privacy-extension.md.

aleo-types: new InputRequest, RecordFilters, RecordFieldFilter,
TransactionInput types with isLiteralInput / hasInputRequest helpers.
TransactionOptions.inputs widens from string[] to TransactionInput[].

aleo-wallet-standard: new ConnectOptions, RecordAccessGrant, ProgramGrant,
RecordGrant, FieldGrant (with readAccess), ViewKeyExposure, plus a
hasUnsupportedConnectOptions helper. ConnectFeature.connect and
WalletAdapterProps.connect accept an optional fourth options argument.

aleo-wallet-adaptor/core: BaseAleoWalletAdapter.connect accepts options,
enforces the readAddress: false / decryptPermission: NoDecrypt precondition,
tracks _readAddress, and short-circuits decrypt, requestRecords,
transitionViewKeys, requestTransactionHistory under address withholding.
New error classes: WalletInputRequestNotSupportedError,
WalletConnectOptionsNotSupportedError, WalletAddressWithheldError. The new
types are re-exported from core for dapp ergonomics.

Wallet adapters: leo, fox, soter, puzzle widen connect with options? and
throw WalletConnectOptionsNotSupportedError when any of the new options are
set; their executeTransaction throws WalletInputRequestNotSupportedError
when any input is an InputRequest. Shield forwards options to the
extension and tolerates an empty address under readAddress: false.

react: AleoWalletProvider accepts new optional props recordAccess,
viewKeyExposure, readAddress and forwards them on every adapter.connect
call. Dependency arrays updated.

Doc: clarified that Account.address returns "" (empty string) under
readAddress: false rather than null, and that FieldGrant.readAccess
controls plaintext exposure independently of filterability.

Implement wallet-specified record inputs and address permission grants

…lues

Adds a fourth `InputRequest` variant `{ type: "derived", algorithm, args }`
that asks the wallet to run a named cryptographic algorithm over its own
state (view key, wallet-maintained counters, etc.) plus dapp-supplied args,
and substitutes the result into a transaction input slot. The dapp never
observes the wallet-side inputs — only the output.

Strict opt-in via a new `algorithmsAllowed?: AlgorithmGrant[]` field on
`ConnectOptions`: each grant authorizes exactly one
`(algorithm, program, function, inputPosition)` call site, all four fields
required and exact-match. The wallet refuses every derived request whose
tuple is not present. No broad default.

A new `algorithmsSupported(): Promise<string[]>` adapter method lets dapps
discover what a wallet implements before populating the allowlist.
Wallets without derived-input support return `[]` (default) and connections
with non-empty `algorithmsAllowed` throw `WalletConnectOptionsNotSupportedError`
via the existing `hasUnsupportedConnectOptions` path.

Inaugural algorithm: `program-scoped-address-blind`. Inputs: `{ "domain-separator": field }`.
Output: `address`. Valid slot positions: `address`, `group`, `scalar`, `field`.

Updates the PrivateInputs example with a fourth `Derived` mode on primitive
slots whose baseType is in an algorithm's `validSlotTypes`, plus a
connect-time `AlgorithmGrant[]` editor with an "Auto-grant this function's
eligible slots" convenience button. The grant JSON preview now includes
`algorithmsAllowed`.

See docs/adapter-privacy-extension.md §"Derived inputs" for the spec and
docs/dapp-privacy-quickstart.md for an implementor's guide.

…Constraints

…or split

…ProvableHQ/aleo-dev-toolkit into examples/private-inputs-example